Open
Conversation
lmbollen
force-pushed
the
lucas/bump-vivado
branch
2 times, most recently
from
8ed97b2 to
6bf02cf
Compare
Contributor
|
Can you run all tests once by copying |
lmbollen
force-pushed
the
lucas/bump-vivado
branch
from
d373b3b to
bcb0b4b
Compare
We're running into issues where CI runners are killed during synthesis because they run out of memory. Previous to this commit both of our build servers had 16 runners (one per CPU core), which had to share a total of 192GB of memory. To also leave some headroom for system overhead, each runner had 11GB of memory. Both build servers now have 12 runners, so each runner can have 15GB.
lmbollen
force-pushed
the
lucas/bump-vivado
branch
from
bcb0b4b to
802bb8e
Compare
For new `gig_ethernet_pcs_pma` without version restriction
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What (what did you do)
Bump vivado to 2025.2
Why (context, issues, etc.)
old vivado bad (
new is also bad, but at least does not use 50gb ram)